Release v1.0.2#138
Merged
Merged
Conversation
Bump version from 1.0.1 to 1.0.2 across pyproject.toml, src/dvoacap/__init__.py, the README badge/header, and the INSTALL_GUIDE expected-output samples. Add a CHANGELOG entry summarising the 1.0.2 contents: * Long-path signal/SNR fix (PR #137). * TX power propagation to user-added antennas (PR #137). * Dashboard-button SyntaxError fix (PRs #134, #135). * Smooth analytic gray-line band (PR #136). * Regression tests for the prediction engine (PR #137). * Dashboard packaged as installable subpackage with dvoacap-dashboard CLI entry point (PR #133). Historical references to v1.0.1 in CLUB_PRESENTATION, NEXT_STEPS, PRESENTATION_GUIDE, KNOWN_ISSUES_CORRECTED, RELEASE_NOTES_v1.0.1.md, and GITHUB_RELEASE_v1.0.1.md deliberately left untouched -- they describe past releases. https://claude.ai/code/session_01BLfWHK9hf8k4aBBaQjfQa8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump version from
1.0.1→1.0.2in:pyproject.tomlsrc/dvoacap/__init__.py(__version__)README.mdbadge + headerINSTALL_GUIDE.mdexpected-output samplesAdd a
## [1.0.2] - 2026-05-01section toCHANGELOG.mdsummarising the user-facing fixes since v1.0.1:_evaluate_long_modelstub into predictions for paths > 7000 km, eliminating constant-0.7 dBWsignal levels and absurd ±150 dB SNRs that the dashboard was rendering.select_antenna(), leaving 100 W radios treated as 10 W).const nowdeclaration that produced aSyntaxErrorand prevented the entire<script>from parsing has been renamed.dvoacap-dashboardCLI entry point (pip install dvoacap[dashboard]works).Historical references to v1.0.1 in
CLUB_PRESENTATION.md,NEXT_STEPS.md,PRESENTATION_GUIDE.md,KNOWN_ISSUES_CORRECTED.md,RELEASE_NOTES_v1.0.1.md, andGITHUB_RELEASE_v1.0.1.mdare deliberately left untouched — they describe past state.Post-merge steps (manual)
After this PR merges, on
main:git tag -a 1.0.2 -m "v1.0.2: dashboard fixes + long-path SNR fix" git push origin 1.0.2Then in GitHub UI: Releases → Draft new release → pick the
1.0.2tag → paste the new CHANGELOG section as the body. If your PyPI release workflow is wired to tag pushes (perPYPI_RELEASE_GUIDE.md), it'll auto-publish.Test plan
python -c "import dvoacap; print(dvoacap.__version__)"reports1.0.2git grep '1\.0\.1'shows only intentionally-historical references (CHANGELOG## [1.0.1]heading, README's "Performance (v1.0.1)" attribution, the v1.0.1 release-note files)pip install --force-reinstall "dvoacap[dashboard] @ git+https://github.com/skyelaird/dvoacap-python.git@1.0.2"installs cleanly and reports v1.0.2https://claude.ai/code/session_01BLfWHK9hf8k4aBBaQjfQa8
Generated by Claude Code